Prepare v1.1.0-rc1 with an opt-in Home Assistant Beta add-on - #85
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare
v1.1.0-rc1so volunteers can test the merged V2 key-recovery changes from #84 through Home Assistant. The existing stable add-on stays on1.0.2; its manifest, settings, and update target are unchanged.Add Roborock Local Server Beta as a separate, opt-in add-on with its own slug and persistent data. It selects the
1.1.0-rc1image, is marked experimental, and defaults to manual startup. The setup guide explains the initial configuration/cloud import, shared-port handling, later Beta updates, and returning to stable. Complete V2 onboarding and MQTT connectivity still need hardware validation.Synchronize the package/module version and lockfile, and make the version checks distinguish stable from prerelease add-ons. Prerelease publishing explicitly excludes the
latest, major, and minor image aliases, using both the GitHub prerelease flag and the tag suffix.Validation:
1.1.0rc1.v1.1.0-rc1.git diff --checkpassed.origin/main.After merging, publish a GitHub prerelease tagged
v1.1.0-rc1from the merged commit. Wait for the release workflow to publishghcr.io/python-roborock/local_roborock_server:1.1.0-rc1for amd64 and arm64 before directing testers to install Beta. Testers opt in once; subsequent Beta builds use Home Assistant's normal update flow.